Release 10.1A: OpenEdge Data Management:
DataServer for ORACLE

Deploying a schema holder

The guidelines and techniques that apply to deploying an OpenEdge database apply to deploying a schema holder for an ORACLE database. There is, however, an additional consideration. Make sure that you make changes to both the supporting ORACLE database and the schema holder. For example, when you provide an SQL script to modify an ORACLE database, you must also provide a new data definitions file or 4GL code to update the schema holder. Keep in mind that the SQL script that you send to a customer’s site must consider how the ORACLE database is configured on their system, including table space and security issues.

There are two techniques for updating a deployed schema holder:

Allow your users to use the DataServer Update/Add Table Definitions utility.
Send a new data definitions file for the schema holder. Your users can load the .df file into an empty OpenEdge database.

To maintain a deployed DataServer application:

Make changes to the ORACLE database.
Run the Update/Add Table Definitions utility on one schema holder.
Run the PROUTIL utility to truncate the before image (.bi) file.
Recompile code against the updated schema holder to build new r-code.
Send out copies of the new .r files and the schema holder .db and .bi files to your users.

You can improve the performance of a deployed application by using the -Dsrv skip-schema-check startup parameter. See the "Skipping schema verification" section for more information.